Jak wystartowac eggdropa0.9r
1 Przegraj go na konto unixowe
2 pisz
gunzip eggdrop0.9r.tar.gz
tar -xvf eggdrop0.9r.tar
cd eggdrop0.9r
./configure
make
mkdir
putegg
pico egg.config.dist (najlepiej zkonfigurowac to juz wczesniej czyli pod dosem off-line, pod byle jakim edytorem)
jesli konfigurujesz on line to by skonczyc Ctrl-X i potem y
pozniej zmien nazwe egg.config.dist na nicka jakiego ustawiles dla bota
eggdrop -m nick
mozna tez off-line skonfigurowac motd i nne pliki tekstowe i przegrac na konto.
act - cos jak /me na kanale.
@ die - zabija boty
me - pisze /me na party line
msg - priv mag do nicka od bota.
op - bot daje opa poki bot jest opem
say - bot mowi na kanal
@ set [value] -ustawianie mozliwych variablesow.
log-time strict-host ignore-time helpbot
clear-bans isolate nick helpdir
op-on-join keep-all-logs username tempdir
revenge chan-updates realname channel-key
greet raw-files home-channel notify-newusers
learn-users perm-bans userfile console
require-x upload-to-cd dcc-path chanmode
require-p telnet dcc-incoming default-flags
enforce-bans servlimit motd never-give-up
use-info flood-msg admin open-telnets
bitch flood-chan gain-ops idle-kick
share-users flood-join init-server ctcp-finger
passive ban-time notefile ctcp-version
dcc-block dcc-maxsize textdir owner
protect-ops forbid-bans keep-nick
who [tandem-bot] -lista ludzi na kanale. * to master
a 'who' wypisuje 3 rzeczy.
1. lista ludzi na kanale.
2. lista poslaczonych botow.
3. lista uzytkownikow, ktorzy nie sa na kanale.
%[ %]
%[ masters may also see "(con)" and/or "(talk)" after a user's%]
%[ entry -- "(con)" shows that user's console modes (see the%]
%[ '.console' help page), and "(talk)" means that user is using%]
%[ the enhanced talk ircII script.%]
%B file transfer commands: (wildcard expressions are allowed)
get [nick] - wysyla plik przez irc
pending - listuje transwer plikow
cancel - rezygnuje z transferu
ls - lista plikow w katalogu
pwd - pokazuje katalog
cd - zmienia katalog
desc - opisuje plik
quit - wychodzi z wysylacza plikow
%[Masters only:%]
%[ import [flg] add to the public file list%]
%[ (if it's a directory, make it require [flg] to access)%]
%[ hide remove from the public file list%]
%[ rm erase the actual file%]
%[ mv move a file to a new location%]
%[ cp copy a file to a new location%]
%[ mkdir [flg] create a new directory (that requires [flg])%]
%[ rmdir erase an existing directory%]
(To upload a file, just start your dcc transfer.)
%B party-line commands:
.quit opuszcza party line
.whom [channel] pokazuje liste uzytkownikow party line
.whom * lista wszystkich na party line
.chat przenosi do kanalu 0d 0 do 99999
.me /me na partyline
.note /msg do nicka
.query query do kogos
.help nie ma
The following commands are also available:
bots newpass email files who echo
bottree botinfo info away notes
Wszystko co puscisz bez . pojdzie do kazdego na party line
@ set admin "" - info o szefie np:
set admin "Robey "
@ set ban-time <#> - jak dlugo ban czasowy ma trwac
@ set bitch <0/1> - tylko ludzie z o maja boty i zadna komanda bota nie dziala dopuki uzytkownik nie ma hasla.
@ set clear-bans <0/1> - mowic czy bot po dostaniu opa ma zlikfidowac bany.
@ set ctcp-version "" iod na ver. np
ircII 2.8 Linux 1.2.4 :ircii 2.6: almost there...
@ set default-flags
specifies the flags to give to a user when they first
introduce themselves to the bot with /MSG HELLO. obviously
this has no effect if you have 'learn-users' turned off.
for a list of the flags, see 'whois'.
@ set enforce-bans <0/1> mowi kiedy ma banowac, czy gdy ich user@host zgadza sie z ban list
@ set flood-msg <#> - flood reply
@ set forbid-bans <0/1> wywala wszystkie zastane bany i mozna tylko banowac przez bota.
!master
@ set gain-ops "" - co wyslac do servera, gdy bot nie ma opa , a inni maja.
@ set greet <0/1>
specifies whether the bot will automatically "greet" users who
have specified an info line, when they join the channel. each
user can set a sort of "bio" line for themselves using the
'info' msg command. if 'greet' is on, when the user joins the
channel, the bot will send their info line to the channel. if
the user's nickname is not in the info line, the bot will add
it. if you have set 'use-info' off, this seting is meaningless,
and users may not set their info anyway.
@ set home-channel - kanal bota
@ set idle-kick <#> - ile minut zanim wykopie klijenta, 0 by to wylaczyc.
@ set ignore-time <#> - ile minut ma ignorowac gnoja
@ set init-server "" - co ma przy polaczeniu napisac na server(najlepiej wlaczyc +i)
@ set isolate <0/1>
specifies whether the bot's party line will be isolated or be
merged with the joint party line created by a set of tandem'd
@ set keep-all-logs <0/1>
specifies whether to keep logs older than 48 hours or not. if
this is set off, at midnight, the current logfile will be re-
named to "(logfile).yesterday" and a new logfile started. the
old "(logfile).yesterday" will be erased. if this is set on,
at midnight, the current logfile will be renamed to "(logfile).
(date)" and a new logfile started. eventually your directory
will be full of files like "LameBot.log.14Jul94".
@ set learn-users <0/1>
specifies whether the bot will add users on the fly when they
send the "hello" msg. if turned off, the only way to add users
is with the '.adduser' or '.+user' commands. if turned on,
users can introduce themselves without your intervention.
@ set log-time <0/1> - okresla czy nadawac czas do log entries czy nie.
@ set motd
specifies the "Message Of The Day" file. this should be a
text file. it will be displayed to users as they enter a
dcc chat session with the bot (so it shouldn't be TOO long).
there are a few %-variables you can insert into the motd,
which will be interpreted by eggdrop:
%%B bot's nickname (ie, "%B")
%%V current eggdrop version (ie, "%V")
%%C channel the bot is on (ie, "%C")
%%A whatever is set in 'admin' (see 'set admin')
%%T the current time (ie, "%T")
%%N the current user's nickname (ie, "%N")
%%%% a percent sign ("%%")
you can also encode messages just for ops or masters:
%%(Anything between "%%(" and "%%)" is shown only to ops.%%)
%%[Anything between "%%[" and "%%]" is shown only to masters.%%]
@ set never-give-up <0/1>
specifies whether the bot should loop forever. If never-give-up
is set false, then the bot will shut down if it goes through the
entire server list once without getting a connection. This is to
keep eggdrop from going through an endless loop, if, for example,
your machine gets disconnected from the rest of the net. However,
some people prefer their bot to never shut down, no matter what.
@ set nick - default nick dla bota
@ set op-on-join <0/1> - wl/wyl opa na join dla 'o' users.
@ set open-telnets <0/1>
specifies whether to accept new users via a telnet connection.
if set to 0, the bot will only accept telnet connections from
people who already have user records. if set to 1, someone can
enter "NEW" after telnetting to the bot, and create a new user
record.
@ set owner ""
specifies the user(s) who are to ALWAYS be bot owners. it
is impossible to remove the +n flag from anyone listed here.
if the bot was compiled with the owner flag turned off, this
variable has no significance.
@ set passive <0/1>
specifies whether the user data sharing of this bot (set share-
users must be on) will be "passive" or "aggressive". a passive
bot will always download the user file from another bot. an
aggressive bot will always upload its user file to other bots.
therefore, two aggressive bots will be unable to share user data.
two passive bots will be able to share, however -- the bot that
did the actual link will be the one to download. (setting both
bots passive allows the user file of the bot which has been
online longest to take precendence, usually.)
@ set perm-bans <0/1>
specifies whether the bot's ban list should be mirrored in the
channel or not. if perm-bans is on (1), the bot will make sure
every ban in its internal ban list is active on the channel.
if you have a large ban list (i've heard of one bot that had
over 200), this could be a big pain. with perm-bans off, the
bot only makes a ban active on the channel if someone joins who
matches one of its internal bans. the ban will then "expire"
(be removed from the channel) after about an hour, or whatever
length of time you specified in 'ban-time'.
@ set protect-ops <0/1>
specifies whether the bot should automatically re-op users who
get deopped. it could be a security hole since no password is
required to regain ops this way.
@ set raw-files <0/1>
specifies whether to provide a 'screen' between users and files
in the file area. if this is on, the file area will deal with
the files directly, as they are found in their directories, and
will not store file descriptions, etc. if this is off, the file
area will create a hidden file in each directory, where it will
store file descriptions and other info. the benefit of raw-files
is that you will not have to 'import' files in a pre-existing
file area. the downside is that you will not be able to use
file descriptions, or track who uploaded what file, and how many
times it has been downloaded. if raw-files is on, the file area
commands 'hide', 'import', and 'desc' are disabled.
@ set realname "" - ustawiasz teoje prawdziwe nazwisko.
@ set require-p <0/1> - mowi czy user z 'o' potrzebuje 'p' by dolaczyc do party line.
@ set revenge <0/1> - wl revange mode, msci sie za gnoj, a jak wyl to tylko loguje gnoj, ktory ktos sieje.
but will sit quiet and do nothing.
@ set servlimit <#>
specifies the minimum number of servers the bot should accept.
if the bot's home channel ever empties out, and the number of
servers on the irc net becomes less than the 'servlimit', the
bot will jump to a new server. this is to prevent it from
getting stuck on the wrong end of a netsplit. to disable it,
just set it to 0.
@ set share-users <0/1>
specifies whether the bot should ever share user data with another
bot. if this is on, it will use each bot's 's' flag to determine
whether or not to share user data. if this is off, all user data
requests are automatically refused.
@ set strict-host <0/1>
specifies whether the bot should leave leading ~ in users' host-
names. if this is on, leading ~ will be left in (the bot will
differentiate between valid-ident usernames and invalid ones).
typically this is set off, since most sites are not running the
ident protocol, and therefore may get ~ put in front of their
username when their username is valid.
@ set telnet
specifies the port # that eggdrop should listen to for telnet
connections, and bot links. once the bot has been loaded,
it's really too late to change this.
@ set tempdir - ustala temp dir, gdzie ludzie beda przerzucali pliki(to nie jest dcc-get dir).np "/tmp".
@ set textdir - log dir.
@ set upload-to-cd <0/1>
specifies whether uploads to the bot's file area go to the
user's current directory (1), or to the directory specified
in 'dcc-incoming' (0).
@ set username
specifies the username the bot will try to use on IRC. if
your machine is running ident, this won't work, and the bot
will show up as the user who started up the bot.
@ set console - jakie default console mode maja miec mastery i ops kiedy pierwszy raz zrobia DCC-chat, see 'console'.
@ set ctcp-finger "" - osp bota na finger np:
Robey (robey@wc130), idle 0 seconds
@ set dcc-path
specifies where the bot's dcc file directory is. if you don't
want a file transfer section on your bot, define this as "".
otherwise, the directory given will be the root directory for
users in the file section. they may move into any subdirectory
and download any file you make visible, but may never move out
past the dcc-path directory.
@ set flood-chan <#>
specifies the flood threshold for channel messges. if the
same host talks on the channel more than this many times
consecutively within 60 seconds, it's considered a flood
and the user is kicked off the channel.
@ set helpbot
specifies the nickname to use for a helpbot. if you don't
want a helpbot, set this to "". the advantage of using a
helpbot is that long text files and information get sent
to users through the helpbot, leaving the main bot free to
do channel protection, etc. the disadvantage is that you
now effectively have TWO bots on irc, which some irc opers
get upset about. usually, having a helpbot is more trouble
than it's worth, unless you are running an info server of
some sort.
@ set keep-nick <0/1>
specifies whether the bot will keep trying to regain its nickname if
it is forced to change nicks. if this is on, and you change the bot's
nick on irc through a TCL script or the '.dump' command, then the bot
will change back to its intended nick within 60 seconds.
@ set require-p <0/1> - mowi czy ludzie z 'o' tez potrzebuja 'x' by wejsc w file system.
@ set use-info <0/1>
specifies whether to activate the info system. if this is off,
the bot will not accept changes to any user's "info line" (the
line shown for '/msg whois' and '/msg who' requests, and shown
when a user joins the channel is you have set 'greet' on).
this disables '/msg whois' and '/msg who' obviously, and makes
the setting of 'greet' meaningless.
@ set dcc-incoming
specifies the directory where files dcc'd to the bot will go.
if you have turned off the file section by setting 'dcc-path'
to "", then this has no effect since all files offered by dcc
to the bot will be rejected anyway. if you have set the
'upload-to-cd' to 1, then this will be ignored, and all files
uploaded (sent) to the bot will go into whichever directory
the user is in currently, or was in last.
@ set flood-join <#>
specifies the flood threshold for channel joins. if the
same host joins the channel more than this many times
consecutively within 60 seconds, it's considered a flood
and the host is site-banned.
@ set helpdir
specifies the path to the help/ directory for the bot. if
you can read this, it was set right. :)
@ set notefile
specifies the filename where bots should store notes that
are sent to someone who isn't on the party line currently.
normally, you don't want to change this after the first
time you load the bot. if you want to disable note storage,
set this to "".
@ set userfile
specifies the filename where eggdrop should store user
records. you normally don't want to change this once you
have started using the bot.
@ set dcc-limit <#> - ile plikow mozna sciagac na raz(1-99)
@ set notify-newusers ""
specifies who to inform when the bot gets introduced to
new users via the /MSG HELLO command. obviously this has
no effect unless the /MSG HELLO command is activated.
the bot will send a note (see 'note') to each user listed
in notify-newusers. this can be just one nick:
set notify-newusers "Robey"
or several, separated by commas:
set notify-newusers "Guy, Eden@Priscilla"
if you don't want anyone to be informed, just set it to
"".
@ set chan-updates <0/1>
specifies whether to show lines like this
10 members, 4 chops, 5o 0m 0d, 14 bans
every five minutes, giving information about the channel.
these "update" lines tell how many people are on the channel,
and how many of them are channel-ops. it also tells how many
people have +o, +m, or +d on the bot, and how many bans are
on the channel.
@ set dcc-block <#> rozmiar block size in DCC (512 lub 1024)
@ set channel-key
specifies the default channel key for the channel your bot
is supposed to be on. most of the time, this can be set
to "". however, if your bot's home channel is usually
protected with a channel key, you need to set this to the
key that is normally used, so that the bot can enter the
channel.
@ set dcc-maxsize <#> max roamiar pliku, jaki przyjmie bot(1024=1mb)
@ set chanmode ""
specifies the channel modes that the bot will enforce on
its home channel. this should be a string just like you
would use in an irc /MODE command. here are some examples:
set chanmode "+nt-l"
(always make channel +nt but always remove a limit)
set chanmode "+k toblerone"
(make sure the channel key is always "toblerone")
set chanmode "-mi+lk 23 toblerone"
(don't let the channel be set to moderated or
invite-only, and keep the limit at 23 and the
channel key as "toblerone")
# -ban - usowa ban
@ -bot
is exactly the same as '-user', but is included for convenience.
it erases a user record.
@ -host
removes a hostmask from a user's record on the bot.
@ -ignore - usowa ignore.
@ -info - usowa info o uzytkowniku.
@ -user
erases the user record for the nickname given.
# +ban [comment] - banujesz
@ +bot
creates a user record for a tandem bot with the nickname given.
the hostmask table have one entry ("none"), and the tandem (t)
flag will be set for the user. the internet address field of
the user will also be set to the address given. you can use
this command and 'chpass' to completely set up a record for a
future tandem bot.
@ +host
adds a hostmask to a user's record on the bot. the hostmasks
are where the bot will identify that user from. usually you
will not need to use this command since a user can add hostmasks
to her own record via the /MSG IDENT command. but it's here if
you need it.
@ +ignore - wl ignore na kogos.
@ +user
creates a new user record for the nickname given, with one entry
in the hostmask table. the new user record will have no flags
(ie, not be a master, op, friend, etc) and no password.
# addlog
writes your comment into the bot's log file. bot masters can go
back later and review the log, and will see your comment (with your
name attached). this is useful for explaining confusing activity.
@ assoc [ ]
creates a name for a channel. the name will propagate across your
botnet (if you're hooked into one) and can be used instead of the
channel # when changing chat channels (see '.chat'). if you omit
the channel # and name, it will just dump a list of the current
named channels, and their names.
# assoc
wipes out the name for a channel, if there was one.
# away [away-message]
marks you as "away" on the party line. your away message will
show up in the '.who' list, and will be displayed to anyone who
tries to send you a note. your notes will be stored, and then
displayed to you as soon as you are no longer away. saying
something on the party line will automatically remove your "away"
status, or you can type '.away' by itself.
@ banner
displays a message to everyone currently using the bot's party line
or file area -- useful for announcing that the bot will go down, etc.
@ binds
shows the TCL bindings in effect, in a list similar to this:
Command bindings:
TYPE FLGS COMMAND BINDING (TCL)
msg - rose msg_rose
msg - go msg_go
dcc m bind cmd_bind
pub - gross pub_gross
the fields should be self-explanatory. if not, go read the
file 'ext' for help on the TCL bind command. note that the
builtin commands are now shown.
@ boot [reason]
# boot [reason]
will kick a user off the party line, and display the reason if you
give one. you can attempt to boot someone from another bot (in a
botnet), though it may be rejected if that bot does not allow remote
boots.
# bots
shows the list of bots currently in the tandem-chain. example:
Bots: cEvin, ruthie, Killa1
there is no indication of which bots are directly connected to
this one. use 'who' or 'bottree' for that information.
# chat off
# chat
changes your channel on the dcc chat connection. when you first
connect to the bot, it places you on channel 0 (the party line).
you can move to another channel where basically nobody can see
you (except anyone else who decides to join that channel). valid
channel numbers are 1 thru 99999. some channels may have assigned
names -- for those, you can specify the channel by name instead of
number if you wish.
'chat off' removes you from any channel at all. you can still
use normal bot commands and see the console, but you can't talk
to anyone except via '.note'
'chat on' returns you to the party line (channel 0) if you were
elsewhere.
@ chemail [email address]
sets the email address for a user. this info isn't really used by
the bot for any reason except to display.
@ chinfo [info-line]
sets the information line for a user. this line is shown via /msg
commands 'who' and 'whois', and if you have set greet on, it is
shown when a user joins the channel. if the info line begins with a
'@', then it is "locked", and that use may no longer change it.
# chinfo none
erases a user's info line.!master
# chpass
changes a user's password on the bot. if you change someone's
password to "nopass", they effectively no longer have a password
set. the password is needed to get ops, join the party line, and
other things (but only required if one is set).
@ comment
creates or changes the comment field for a user. the comment field
can only be seen via 'user' or 'match' -- non-masters can never see
user comments.
# console [modes]
changes your console level, so that you will see only those types
of console messages that you want to. valid levels are:
m display private msgs/ctcps to the bot
p display public talk and ctcps on the channel
k display kicks/bans/mode changes on the channel
j display joins/parts/nick changes/signoffs/etc on the channel
b display bot links/unlinks/userfile-sharing
%[ c display user commands (dcc and msg)%]
%[ x display file transfers and file-area commands%]
%[ o display other bot notices [HIGHLY RECOMMENDED]%]
%[ (note that only masters may use 'c', 'x', or 'o'.)%]
the mode can also be a modifier like '+p' or '-jk' or '+mp-b'. if
you omit the modes, it will show you your current console setting.
%[### console %]
%[ is used to set the console level of another user. this can even%]
%[ be used on users who normally would not be able to set their own%]
%[ console mode.%]
@ dccstat
displays a table-format list of all the "dcc" connections the bot
is handling. "dcc" means "direct client-to-client communication"
and eggdrop expands this to cover every open socket. so any type
of network connection to the bot is considered a "dcc" connection
(except connections to a server). the headings of the table are:
## the index into the dcc-table (always starts at 0)
SOCK the socket of this connection (always unique)
ADDR the IP-number of the host the connection is to, if
applicable
PORT the port number being used for communication
NICK the nickname of the user or bot, if it's a user or bot
HOST sometimes, the hostname corresponding to the IP address
TYPE the type of dcc connection (see below)
the types of connection currently possible are as follows (but
more are being added literally all the time):
chat user in dcc-chat command mode
pass user entering dcc chat (being asked for her password)
send raw data connection: user sending a file
get raw data connection: sending a file to a user
getp pending get (waiting for the user to acknowledge)
teln telnet listening port (there is never more than one)
t-in incoming telnet user (being asked for his nickname)
file user in dcc-chat file area
edit user in dcc-chat editor (must be a master)
tand bot in tandem communication
tnd* pending tandem bot (waiting for acknowledgement)
rela user in relay connection to another bot
>rly bot being relay'd to (one for each "rela")
fork pending telnet connection out (forked out)
new new user via telnet, entering a handle
newp new user via telnet, entering a password
@ debug
will display a dump of memory allocation, assuming the bot was
compiled with DEBUG defined. it's useless to anyone but program-
mers hacking on the bot and trying to find memory leaks.
# deop - usowa z opa tak slugo jak bot ma op, chyba ze ktos jest 'o'
@ dump
dumps the text to the server. keep in mind that this bot doesn't
run through ircII, so ircII commands will most likely not work this
way. they need to be raw irc codes.
# echo
sets whether you want your messages echoed back to you. if it's
on, then when you say something on the party line, it will be
displayed to you just like everyone else will see it. if it's off,
then that won't happen.
@ edit
loads the bot's internal editor and lets you edit a file. the
internal editor is very lame, and difficult to deal with at best.
if you have compiled with an external editor defined, that will
be used instead (usually "red").
# email [email address] - ustalasz swoj e-mail address
# files
will move you into the file transfer sub-system, if it has been
enabled on this bot. from there you can browse through the
files on-line and use dcc file transfers to download and upload.
@ handle
changes the handle/nickname of a user record. for example, to
change the nickname of user 'gavroche' to 'jamie', you would
type: 'handle gavroche jamie'
DCC COMMANDS for %B, %V:
who +ban say away quit
whom -ban msg me servers
whois bans act note channel
match resetbans motd files kick
bots op addlog newpass kickban
bottree deop invite console chat
notes topic nick email info
echo
%[For masters only:%]
%[ handle +user link status die%]
%[ chpass +bot unlink dccstat dump%]
%[ chattr +host trace debug +ignore%]
%[ comment chinfo banner set ignores%]
%[ chemail save boot rehash jump%]
%[ adduser binds relay reset edit%]
%[ chaddr %]
%[(Any commands starting with '+' may be preceded by '-' instead.)%]
All commands begin with '.' and all else goes to the party line.
%[Text starting with ',' is sent ONLY to bot-masters.%]
You can get help on individual commands: '.help '
# ignores
lists the hostmasks that the bot is currently discarding msgs,
etc from. the ignores are numbered, so they can be easily
removed with '-ignore' by number. a permanent ignore looks
like this:
[ 1]: *!robey@* (perm)
this kind of ignore can only be stopped by using '-ignore'.
a temporary ignore looks like this:
[ 2]: *!*@ohio.eng.clemson.edu (active 3:19)
that means the ignore was made automatically by the bot three
minutes and 19 seconds ago, probably because of some sort of
flooding. it can be removed with '-ignore', or it will expire
after it has been active a certain amount of time (specified
by 'ignore-time').
# info [info-line]
sets your info line. this is shown via /msg commands 'who' and
'whois', and possibly when you join the channel. if you omit the
info line, it will just show you what your current info line is.
# info none
removes your info line.
# invite
invites someone from irc into the bot's home channel. this is
most useful when the channel is +i. a user with the +o flag can
also request an invite from the bot with /MSG INVITE
@ jump [server [port]]
makes the bot jump to another server. if you don't specify a
server, it will jump to the next server in its internal list (see
'help servers'). if you specify a server, it will jump to that
server (default port is 6667), and if that server is not in the
internal list already, it will add it. jumping servers ALWAYS
makes the bot lose ops!
# kick - kick z kanalu.
@ link
makes this bot attempt to telnet across to the specified tandem
bot and bring the two bots into tandem. the tandem-bot must have
a user record with an internet address, and a password which is
used to validate the connection. if a bot is tagged with the
"friend" flag (f), a connection is attempted automatically every
60 seconds until success, so you don't have to use this command
for "friend" tandem-bots.
# match + [[start] limit]
shows you user records which have the attributes listed (such as
'.match +of' to show all users who are friends and ops)
# match [[start] limit]
shows you user records where the nickname or any of the hostmasks
match the wildcard string shown.
the default limit is 20, meaning that if more than 20 user records
match your requirements, only the first 20 will be shown. you can
change this limit by specifying one on the command line, though.
if you include a limit, you may also include a starting place (the
default is 1). for example, to list the first 15 users who have
hostmasks from clemson.edu:
.match *clemson.edu 15
to get the next 10 (if there are more than 15), you ask to list
numbers 16 thru 25:
.match *clemson.edu 16 25
# motd
will redisplay the party-line message of the day, which was
shown when you first joined.
# newpass - zmiana hasla
# nick
changes your nickname on the bot. that's the handle that the bot
will know you as forever and ever, and what you have to use when
telnetting in or IDENT'ing yourself, so remember it.
# notes index
# notes read <# or ALL>
# notes erase <# or ALL>
lets you manipulate notes that have been stored up for you while
you were gone. 'notes index' gives a listing of all the notes
stored up: who they are from, and when they were left. 'notes
read' lets you read a particular note, or all of them at once.
and 'notes erase' erases notes after you are done with them.
%B party-line commands:
.quit leave the party line
.chat <#> change chat channels: "secret" channels are
1 - 99999; the party line is 0
.me do an action on the party line
.note send a private note to someone else on the
party line
.whom [channel] see who's on your current channel -- if
you specify a channel number, show who's
on that channel
.whom * see total list of people online
.who [bot] list only the people on a specific bot
.motd re-view the message of the day
.files enter the file system (if it's available)
.away mark yourself as 'away' (notes to you will
be stored until you return)
.newpass change your password on the bot
Anything you type that doesn't begin with a '.' goes out to
everyone on the party line.
--- End of help.
# quit - usowa cie z party line i rozlacza dcc.
@ rehash
reloads the config file for the bot, which resets all the 'set'
variables and reloads any TCL scripts your config loads. it
also reloads the user file from disk, which will only have an
effect if you have set 'periodic-save' on
@ relay
will relay you via telnet to a tandem-bot that this bot knows of,
whether or not they are currently connected. your dcc-chat/telnet
connection to this bot will be relayed to the other bot until the
other bot drops your relay, or until you send "*bye*" on a line by
itself.
@ reset
clears out the bot's channel information and makes it gather the
information from the server all over again, as if it had just
joined the channel. it's not really useful much, but could be
if an odd bug causes the channel information to get scrambled.
unfortunately this command used to get a lot of use.
@ save
makes the robot write its entire user list to the disk. this is
useful if you are running with "periodic-save" on (meaning the bot
only saves the user list once an hour) and you have just made some
major changes to the user list and want to make sure they're stored
on disk, for safety.
# servers
lists the servers that the bot has in its server list. this is
the list it rotates through when changing servers. it starts
with a static list which it loads from its config-file when the
bot is booted up. after that, you can add servers with the
'.jump' command. the server list will indicate which server the
bot is currently on, and, if a helpbot is running, which server
the helpbot is on.
# simul
if the user is on the party line, the bot will simulate them typing
the text you specify. example:
.simul dweeb .quit
makes it just as if "dweeb" typed ".quit"
@ status
# status all
displays a condensed block of information about how the bot
is running. here's an example from Snowbot:
I am Snowbot, running eggdrop v0.9n (under Linux/Tcl).
Admin: Robey
Channel #turtle, 2 members, 400 users, mode +tn (mem: 42k)
Server minnie.cc.utexas.edu:6667
Online for 4 days, 06:18 (background) CPU 14:18 cache hit 55.3%
Mode(s): revenge, greet, learn users.
the first line tells you the bot's name, and what version of
eggdrop it's running.
the second line, if present, is the contents of your 'admin'
line in the config file.
next is the channel the bot is on (which will be preceded by
"Desiring" if the bot is not currently on the channel), the number
of people on the channel, the number of users the bot has records
of, the current channel mode, and the amount of memory being
allocated to all this info.
if the bot isn't currently a chanop, it will say so in the status
info here, and send out the 'gainops' string (from the config file)
and ask any linked tandem bots for ops too.
if your bot is sharing user files with anyone, and is currently
either transmitting or receiving the userfile from a bot, it will
say so here, and tell how many users have been received so far,
or how many more users need to be transmitted.
the next few lines show the current server, and if the helpbot is
in use, its nickname and current server. to prevent server
flooding, both the bot and its helpbot use queues to store replies
to queries from users. if either queue has a significant amount
of information in it, this status display will show how full (%)
the queue is.
the next line tells you how long the bot has been online, and
whether it is operating in the background or foreground. if it's
in the foreground, it will tell you whether it's in terminal mode
or channel display mode. (terminal mode makes the local console
simulate a dcc chat connection, and channel display mode displays
a '.status' and '.channel' output every few seconds.) it will
also give you an estimate of the amount of CPU time (minutes and
seconds) the bot has used so far, and how well the cache is
working. (the cache is an attempt to keep the CPU time down, and
anything over 50% or so is just great.)
the last line tells any significant modes set with the '.set'
command, like auto-op, revenge, auto-greet, learn users, periodic
save, and userfile sharing modes. (See '.set' for more info on
those things.)
if you do '.status all' you will see another pageful of info,
showing every internal setting as specified in the config file.
it should be self-explanatory to anyone who needs to use it.
# topic
changes the channel's topic, assuming the bot is a chanop or the
channel is not +t.
@ trace
sends out a trace signal to another bot. if that trace signal
returns (and it should!) you will get an output something like
this:
Trace result -> Valis:Stonewall:NoBoty:SomeBoty
it's a list of the bots between you and the destination bot.
@ unlink
disconnects this bot from the tandem-bot specified, assuming they
were connected in the first place.
# whois
will show you the bot information about a user record. there are
five headings:
HANDLE the handle (nickname) of the user
HOSTMASK(S) the hostmasks from which this user is recognized
PASS "(yes)" if she has a password set, "(no)" if not
ATTR the list of flags for this user (see below)
LAST the time or date that the user was last on the
channel
the valid flags under ATTR are:
o op (bot da mu opa)
d deop (nie pozwoli by zostal opem)
k kick (auto. go wykopuje)
m master (user jest masterem)
n owner (user jest wlascicielem)
f friend (user nie bedzie karany za zle tricki)
x xfer (user ma dostep do file area)
t tandem (user jest botem)
p party-line (user ma dostep do party-line)
c common (user record is a common-access site) [see 'help common']
s (BOT) share (bot is sharing user records)
a (BOT) auto (bot is auto-connected)
l (BOT) leaf (bot is a leaf, not a hub)
r (BOT) reject (bot will not be allowed on the net)
h (BOT) hub (only one hub bot will ever be auto-connected)
--- there are also seven user-defiend flags: 1, 2, 3, 4, 5, 6, and 7 ---
if the user entry is for a bot, there will be a line below which
says "ADDRESS:" and gives the bot's telnet address. some user
entries may have "EMAIL:" and "INFO:" entries too.
%[ masters: if there is a comment, you will see it under "COMMENT:"%]
see also: '.match', which will show multiple user records.
@ adduser
creates a new user record for a user on the channel, using their
current hostname. it's similar to a user msg'ing the bot 'hello'
except that no information is sent to that user. if the bot
already knows someone by that nickname, and the user on the channel
doesn't have a bot record, then it does the equivalent of an
'ident' for that user -- except that, again, no information is
sent to the user telling them that anything was done.
# bans [wildcard]
# bans all
shows you the list of permanent bans stored on the bot, and
their respective attributes. here's a sample entry:
[ 5] *!*lamer@*doofus.com (perm) (redbird: ctcp floods)
the number (5) can be used to reference the ban if you wish
to remove it (see '.-ban'). next is the actual hostmask being
banned. the "(perm)" means that the ban is "permenent": that
is, it doesn't automatically expire. if there is an elapsed time
showing instead, the time displayed is how long the ban has been
active. those kind of bans expire after one hour. the last part
of the ban entry is the comment ("ctcp floods") and who put the
ban there (redbird). sometimes there will be a "!" or "*" right
before the number. a "!" means the ban is in the bot's permban
list, but is not currently on the channel. a "*" marks a ban
which is NOT in the perman list but IS on the channel.
if you use 'bans ' it will list all the bans (active
or not) that match against your wildcard. consider it a 'bans
all' list matched against your wildcard.
if you use 'bans' it will show you only the bans which are
currently in action on the channel. if you use 'bans all' it
will show you every ban in memory. (with 'perm-bans' on, these
are identical.)
# bottree
shows a tree-format diagram of the bots currently in the tandem-
chain. it's just a nice way to get a feel for how the bots are
connected physically.
@ chattr [attributes]
lets you view and change the attributes (flags) field for a user.
for example, to give Lamer the p and f flags:
.chattr Lamer +pf
or to remove Denali from the deop list:
.chattr Denali -d
you may also do any combination of the above:
.chattr Fred1 -m+dk-o
whether or not you change any flags, it will show you the user's
attributes afterwards. if this bot uses the owner flag, only the
owner may add or remove the 'n' (owner), 'm' (master), and 's'
(bot: userfile share) flags. to get a list of the flags possible,
do 'help whois'.
# (the +c 'common' flag)
sometimes a lot of people use irc from the same account -- for
example, a telnet site. in that case, a whole bunch of people
will have the same user@host. so they can't use a traditional
user record because they will appear to all be the same person.
in this case, you create a user record for the account, and mark
it +c, or "common access". that means that it shouldn't be used
as a definitive address. when someone introduces herself to the
bot (ie, by /msg'ing "hello"), if she matches as a +c user, she
will be given a new user record which identifies her BY NICKNAME.
obviously people with that kind of user record shouldn't be given
much special access, since when they change nicknames, the bot
will identify them as someone else.
# kickban [comment] - kick + ban
# note
sends a private note to a user on the party line. if that user
is currently on the party line, and not marked as away, she will
receive the message immediately. otherwise it will be stored
and displayed the next time that user joins the party line. if
you join the channel, and have notes stored for you on the bot,
it will tell you. to send a note to someone on a different bot
(which is in tandem with this bot), use "nick@bot" for the
nickname.
# resetbans
makes the ban list on the channel identical to the permanent ban
list stored in the bot. any bans on the channel that aren't in
the ban list will be removed, and if there are any bans stored
on the bot that are not currently on the channel, they will be
added.
# whom
will display a table of the users currently on the joint party
line (formed when you have two or more bots in tandem). it
will show each user's nickname, preceded by a "*" if they are
a master on their bot, or a "@" if they are an op. in other
columns it will show the bot the user is on, and his or her
host. it may take a second for the table to finish displaying,
since it is formed by sending requests to every bot in tandem.
obviously, if your bot is not linked to any other bot, this
command is no different than '.who' (except in format).
if you are on a different channel than the party line (channel
0), then this will show the people on every bot who are on
your current channel.
@ chaddr
changes the internet address for a tandem bot. this is the
address the bot will try to telnet to in order to create a con-
nection and bring the bots into tandem (see 'link').
# channel
shows you an extensive display of the users on the channel, and
the current channel attributes. the first line will look like:
Channel #hiya, 8 members, 45 users, mode +tn: (mem: 9k)
this means that the bot is sitting on channel #hiya, where 8
other irc'ers are. there are 45 people that the bot knows by
hostmask, and the channel mode is +tn. the user list (those 45
users) is taking up 9 kilobytes of memory. if the bot isn't
currently on the channel it is supposed to be on, it will say
"Desiring channel #hiya" instead... next is a list of the users
on the channel, with each entry looking like this:
1. @Trey Trey (23:29) MO harris@random.edu
the "@Trey" means that the user's nickname is Trey and that he
is a chanop. the second "Trey" is the nickname that the bot
knows him by. sometimes this will differ from the nickname a
person is using. the time displayed is the time the user joined
the channel. the next field is the attributes:
I - idle for more than 15 mins O - can get ops (+o)
M - bot master or owner D - cannot get ops (+d)
the last field is the user@host he is using irc from.
@ /MSG %B DIE - zabija bota.
/MSG %B EMAIL - ustawiasz twego e-maila.
MSG commands for %B:
EMAIL INFO WHO IDENT
HELP NOTES WHOIS PASS
%( OP INVITE %)%[DIE JUMP%]
%[ MEMORY REHASH RESET STATUS%]
For help on a command, /MSG %B HELP
%[You are a master. Many many more commands are%]
%[available via dcc chat.%]
Admin: %A
%B party-line commands:
.quit leave the party line
.who [bot] see who's on the party line -- if you give
a bot's name, show who's on that bot
.me do an action on the party line
.motd re-view the message of the day
.files enter the file system (if it's available)
.note send a private note to someone else on the
party line
.query makes it so that whatever you type that would
normally go to the channel goes to this nick
.away mark yourself as 'away' (notes to you will
be stored until you return)
.newpass change your password on the bot
Anything you type that doesn't begin with a '.' goes out to
everyone on the party line.
/MSG %B IDENT - bot rozpoznaje cie z nowego servera, lecz musisz podac haslo ustawione na PASS.
so the bot knows it's really you.
/MSG %B INFO
Whatever you set as your info line will be shown when
you join the channel, as long as you haven't been there
in the past three minutes. It is also shown to people
when they ask the bot for WHO or WHOIS.
/MSG %B INFO NONE - kasuje twoje info line.
!op
/MSG %B INVITE - bot zaprasza cie na kanal.
/MSG %B JUMP [server] - skok do innego servera.
'new.server.com' lub 'new.server.com 6667'.
/MSG %B MEMORY - pokazuje ile uzywa pamieci.
/MSG %B NOTES INDEX - lista wiadomosci do ciebie.
/MSG %B NOTES READ <# or ALL> - pokazuje wiadomosci do ciebie.
/MSG %B NOTES ERASE <# or ALL> - kasuje wiadomosci do ciebie.
/MSG %B NOTES TO
This stores a note to someone, as long as the bot knows
him or her. They will be informed of a note waiting for
them the next time they join the channel.
%B help: (all commands given in /MSG)
WHO : info o wszystkich na kanale.
IDENT : validate yourself from a new user@host
PASS : ustala haslo.
PASS : zmiana hasla
INFO : jakie info o tobie ma pokazac gdy wchodzisz na kanal.
EMAIL : ustaw twoj e-mail
WHOIS : info o innym uzytkowniku.
%( OP : give you op on the channel%)
%( INVITE : invites you to the channel%)
Admin: %A
!op
/MSG %B OP - bot cie opuje.
/MSG %B PASS - ustalenie hasla, gdy to masz mozesz uzywac IDENT.
%( Ops and masters: You need a password to use ANY op or%)
%( master command.%)
/MSG %B PASS - zmiana hasla.
/MSG %B REHASH
This makes the bot reload its config file, etc, just
like the corresponding dcc chat command.
/MSG %B RESET
This makes the bot reset its channel information, just
like the corresponding dcc chat command.
/MSG %B STATUS - maly opis statusu bota, tez z DCC jest duzo lepszy.
/MSG %B WHO - kto jest na kanale i info o nim.
/MSG %B WHOIS - info o innym uzytkowniku bota